Processing event messages for data objects to determine data to redact from a database

ABSTRACT

Provided are a computer program product, method, and system for determining data to redact in an object. Event messages for objects are received. Each event message includes at least one facet, each facet for an instance of data in an object resulting from deep data inspection of the object that is used to determine whether the instance of data should be redacted. The event messages are added to a message queue. Information is added to a database for each of the event messages include the at least one facet for an object in the event message. The database is queried to determine an object having a facet for an instance of data that indicates the instance of data is to be redacted. The instance of data is redacted in the determined object having the facet that indicates the instance of data is to be redacted data.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to a computer program product, system, and method for processing event messages for data objects to determine data to redact from a database.

2. Description of the Related Art

Data objects in a large-scale storage environment may be stored in distributed storage systems. As data is generated and modified at ever increasing rapid speeds and the amount of data exponentially increases, the computational efforts to process data for management purposes based on organizational policies likewise increases.

Many large-scale storage environments store sensitive data, such as personally identifiable information, financial information, health information, etc., that needs to be redacted. Organizations use tools that periodically scan source storage systems to determine data for fields that require redaction. If these fields are found, they are redacted in the data. Enterprise content managers/repositories intercept data in a data path to inspect the data as it is ingested and perform redaction.

There is a need in the art for improved techniques to redact data from documents in a storage environment.

SUMMARY

Provided are a computer program product, method, and system for determining data to redact in an object. Event messages for objects are received. Each event message includes at least one facet, each facet for an instance of data in an object resulting from deep data inspection of the object that is used to determine whether the instance of data should be redacted. The event messages are added to a message queue. Information is added to a database for each of the event messages in the message queue to include the at least one facet for an object in the event message. The database is queried to determine an object having a facet for an instance of data that indicates the instance of data is to be redacted. The instance of data is redacted in the determined object having the facet that indicates the instance of data is to be redacted data.

With the above embodiment, event messages having facets on instances of data object are added to message queues for immediate processing in the queues to update a database to include the facets for the objects in the event messages. The database may then be queried to determine objects having an instance of data that is to be redacted as indicated by the facet for the data object. Because the database is updated immediately with information on objects and their facts directly from the message queues, objects just updated are immediately processed to determine data to redact.

In a further embodiment, a facet that indicates data to redact comprises at least one of sensitive data, personally identifiable information, and financial information.

With the above embodiment, the facets are used to determine objects having certain types of sensitive data that needs to be redacted to remove personal and financial information.

In a further embodiment, an event message in a message queue includes metadata for an object indicating an object is an updated objected. The metadata from the event message for the object is added to the database. The querying the database comprises querying the data for updated objects having facets indicating data that is to be redacted.

In a further embodiment, redaction rules indicate data types to redact. Determining an object having a facet for an instance of data that indicates the instance of data is to be redacted comprises determining whether the facet matches one of the data types indicated in the redaction rules. Data instances having facets matching one of the data types in the redaction rules is to be redacted.

With the above embodiments, the redaction determination is made based on redaction rules to redact data instances having facets matching a data in the redaction rules. This allows for control of what data is to be redacted by specifying data types in the redaction rules.

In a further embodiment, an update on a new data type to redact is received and the database is queried to determine an object having a facet for an instance of data that matches the new data type. The instance of data in the determined object having the facet matches the new data type.

With the above embodiment, new data types to redact may be received to allow immediate determination of data objects having an instance of the new data type that needs to be redacted. This allows for compliance with any regulations that indicate new data types that are sensitive and should be redacted by determining objects having an instance of the data matching the new data type to allow compliance with any new regulations.

In a further embodiment, redaction rules indicate data types to redact, wherein a data instance is redacted having a facet matching one of the data types indicated in the redaction rules. The new data type is added to the redaction rules to be available for the next redaction operation on the data object.

With the above embodiment, redaction rules used to determine data types in objects to redact are immediately updated to reflect new received data types to ensure compliance with any new regulations or best practices for new data types to redact.

In a further embodiment, an event message includes metadata on an updated object, wherein the metadata on the updated object updates metadata for the object in the database, wherein deep data inspection is performed on the updated object to update facets for the updated object that is added to the database.

With the above embodiment, when updating an object, a deep data inspection is performed of the updated data object to determine any updated facets that may reflect data instances to redact based on the recent changes to the object. This allows for immediate redaction of data if new data instances of a data type to redact are added to the updated object by having the deep data inspection process the updated data object to determine any new facets to include in the event message for consideration to redact.

In a further embodiment, event messages are generated immediately after a modification resulting in the updated object to provide information on real-time changes to updated objects to the message queue and the database.

With the above embodiment, providing immediate event messages ensures that the database is updated in real time so objects are timely redacted immediately upon being updated in the database to protect any sensitive data added to the data objects.

In a further embodiment, there are a plurality of message queues and consumer processes. Each of the consumer processes assigned to process event messages from one of the message queues. The message queues receive event messages for objects. A consumer process is periodically revoked to read the event messages in one of the message queues and add metadata and facets to the database for an object indicated in each of the read event messages.

With the above embodiment, the speed of processing event messages is improved by allowing parallel processing of event messages by having separate consumers process the event messages in different message queues to allow for immediate updating of the database with information on the updated objects so that the next data redaction operation will be performed with respect to the newly updated objects possibly having new data to redact.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a storage environment.

FIG. 2 illustrates an embodiment of an event message.

FIG. 3 illustrates an embodiment of database record.

FIG. 4 illustrates an embodiment of a data redaction facet.

FIG. 5 illustrates an embodiment of operations to generate an event message for an updated data object.

FIG. 6 illustrates an embodiment of operations to dispatch an event message to a message queue.

FIG. 7 illustrates an embodiment of operations to process a message queue.

FIG. 8 illustrates an embodiment of operations to determine data to redact from data objects.

FIG. 9 illustrates an embodiment of operations to process a new data type to redact from a redaction update service.

FIG. 10 illustrates an embodiment of message queue subscriber information.

FIG. 11 illustrates an embodiment of operations to provide a notification for an event message added to a message queue.

FIG. 12 illustrates an embodiment of operations to process a notification of an event message added to a message queue to determine whether to redact data in a data object indicated in the event message.

FIG. 13 illustrates a computing environment in which the components of FIG. 1 may be implemented.

DETAILED DESCRIPTION

In large-scale storage environments having files distributed across numerous storage systems, organizations may have difficulty determining data that is required to be redacted, such as personally identifiable information, financial information, health information, etc. One technique to redact data is to scan source storage systems to search for fields in files that require redaction. This technique requires dedication of substantial computational resources to post-process scanning to identify data in files and objects to redact. As part of determining data to redact, a system will scan numerous files, such as billions of files, in the distributed storage and file systems, to determine data to redact, which may change as the file is modified. One problem with current scanning techniques is that as scale of the number of files in distributed file systems increases to several billion files and database records, the time and computational effort to scan objects across different storages substantially increases. Further, performing scanning as part of post-processing may cause delays in redacting sensitive and personal information, which may leave that data exposed to unauthorized access in the file system.

Described embodiments provide improvements to computer technology for redacting data by substantially reducing the time to determine data to redact in modified files by having the source or client systems generate in real-time event messages having information on changed data objects that are sent to a storage server to dispatch to message queues. The event messages are processed from the message queues to add to a database. The database may be queried for changed data objects having facets providing classifications and descriptions of data fields that match data types to redact in data redaction rules. This allows a determination of data to redact very quickly from the database, such as from a fast database index, by determining changed data objects having facets for data instances matching data types to redact.

In this way, a database is populated with information on changed data objects in real-time from messages generated from source systems in real-time, and this real-time database may be searched to immediately determine changed data objects having data to redact to allow for immediate redaction to immediately comply with redaction requirements, which may be promulgated by government and industry organizations.

In a further embodiment, the determination of changed data objects having data to redact may be immediately determined from the message queues by notifying a consumer process when an event message for a changed data object is added to a message queue. The notified consumer process reads an event message from the message queue for which the notification was sent and immediately determines in real-time whether this recently modified data object has data to redact.

FIG. 1 illustrates an embodiment of a storage environment including a storage server 100 that receives event messages 200 (FIG. 2) from source servers 102 ₁, 102 ₂ . . . 102 _(n) that are generated when a source server 102 ₁, 102 ₂ . . . 102 _(n) applies an update to a data object 104 ₁, 104 ₂ . . . 104 _(n) to a storage 106 ₁, 106 ₂ . . . 106 _(n) managed by the source server 102 _(i), where the update to a data object may comprise a delete, modification or adding of a data object. A data object or object 104 _(i) may comprise a file, database object, logical blocks, volume, chunks, extents or any other storage unit in which data may be separately manipulated and addressed. Event managers 108 ₁, 108 ₂ . . . 108 _(n) at the source servers 102 ₁, 102 ₂ . . . 102 _(n) create and send the event messages 200 to the storage server 100 upon receiving a modification to a data object from an application 112 in a host system 110 in real-time before the modification is applied to the storage 106 _(i). In this way, the storage server 100 receives event messages 200 on modifications to data objects immediately in real-time when the changes are made, and in certain embodiments before the changes are applied to the storage 106 _(i).

The source servers 102 ₁, 102 ₂ . . . 102 _(n) include a deep inspection module 109 ₁, 109 ₂ . . . 109 _(n) that processes the data objects 104 ₁, 104 ₂ . . . 104 _(n) and determines facets for data fields or data instances in the objects that provides a description or classification of data instances, also referred to as data fields, that can be used to determine whether the data instance should be redacted. For instance, the facet may indicate that a data field or instance in the object comprises a type of personally identifiable information (e.g., social security number, name, address, phone number, etc.), financial information (bank and credit account numbers), sensitive information, medical information, such as diagnosis and prescriptions, etc. The facet may further indicate data types that do not need to be redacted, such as anything else that is not recognized as data that needs to be redacted in the redaction rules 130.

The deep inspection module 109 ₁, 109 ₂ . . . 109 _(n) may utilize a natural language classification program that collects and analyzes content in the data objects 104 i to provide a predefined classification based on processing of the content in data fields, or data instances. The deep inspection module 109 _(i) may use deep inspection techniques such as IBM® Watson™ Explorer Content analytics, Sentiment Analytics, Contextual Views based on natural language classification as well as Watson™ Application Programming Interfaces (APIs) such as speech to text, visual recognition, etc. These techniques help in capturing metadata information from data objects and determining a classification of the data. (IBM and Watson are trademarks of International Business Machines Corporation throughout the world).

The storage server 100 includes a processor 114, such as one or more processor devices, and a memory 116 having program code executed by the processor 114, including an event message dispatcher 118 to process event messages 200 from event managers 108 ₁, 108 ₂ . . . 108 _(n) and a storage manager 120 to determine an appropriate storage 106 _(i) for modified data objects. The event message dispatcher 118 receives event messages 200 and adds the messages to one or more message queues 124 ₁, 124 ₂ . . . 124 _(m), in the memory 116. For instance there may be a message queue 124 _(i) for each storage 106 _(i) and an event message 200 for an update to a data object at one of the storages 106 ₁, 106 ₂ . . . 106 _(n) is added to the message queue 124 _(i) for the storage 106 _(i) having the updated data object. The memory 116 may further include one or more consumers 126 ₁, 126 ₂ . . . 126 _(m) to process event messages in one or more of the message queues 124 ₁, 124 ₂ . . . 124 _(m) to convert the information on an updated data object in an event message 200 to a database record 300 _(i) (FIG. 3) to store in a database 300.

The storage server 100 includes a data redaction module 128 to redact data fields and instances from data objects 104 _(i) using data redaction rules 130 indicating data types that should be redacted from objects, such as personally identifiable information, financial information, medical information, etc. The data redaction module 128 may perform redaction by making the data fields to redact unintelligible, such as by replacing the data to redact by a meaningless string, blacking out the data with a large blackout rectangle, and/or encrypting the data

In one embodiment, the deep inspection module 109 _(i) may be implemented in the source servers 102 ₁, 102 ₂ . . . 102 _(n) as shown in FIG. 1, where the deep inspection module 109 _(i) may process a data object 104 _(i) to determine any new facets for updated data instances in the updated object 104 _(i). The deep inspection module 109 _(i) reads a data object 104 _(i) from a storage 106 _(i) to perform the data classification. In a further embodiment, the deep inspection module 109 _(i) may be implemented at the storage server 100. In a still further embodiment, the deep inspection module 109 _(i) may be implemented in a separate system or in a hardware device.

There may be any number of message queues 124 _(i) and consumers 126 _(i) to process the message queues 124 _(i), where consumers 126 _(i) may process requests from one or more of the message queues 124 _(i). In certain embodiments, there may be a separate message queue 124 _(i) for each source data set 104 _(i).

The database 300 may comprise a No Structured Query Language (No SQL) database, an SQL database, a relational database, objected oriented database, Extended Markup Language (XML) database, and any other suitable database known in the art.

The storages 106 ₁, 106 ₂ . . . 106 _(n) may be implemented in different types or classes of storage devices, such as magnetic hard disk drives, magnetic tape storage, solid state storage device (SSD) comprised of solid state electronics, EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory, flash disk, Random Access Memory (RAM) drive, storage-class memory (SCM), etc., Phase Change Memory (PCM), resistive random access memory (RRAM), spin transfer torque memory (STM-RAM), conductive bridging RAM (CBRAM), magnetic hard disk drive, optical disk, tape, etc. Storage arrays may further be configured ranks in the storage devices, such as Just a Bunch of Disks (JBOD), Direct Access Storage Device (DASD), Redundant Array of Independent Disks (RAID) array, virtualization device, etc. Further, the storage devices implementing the storages 106 ₁, 106 ₂ . . . 106 _(n) may comprise heterogeneous storage devices from different vendors and different types of storage devices, such as a first type of storage devices, e.g., hard disk drives, that have a slower data transfer rate than a second type of storage devices, e.g., SSDs.

The memory 116 may comprise a suitable volatile or non-volatile memory devices, including those described above.

A redaction update service 132 provides updated redaction data types to redact to the storage server 100 to update the data redaction rules 400, such as new regulatory compliance requirements for redacting data. In one embodiment, the redaction update service 132 may comprise a cognitive news discovery services like the IBM Watson Discovery News service, which tracks latest news on various topics, including new regulatory compliance requirements.

FIG. 2 illustrates an embodiment of an instance of an event message 200 generated by an event manager 108 _(i) to provide to the storage server 100 to use to determine whether to redact data in a data object 104 _(i), and includes a data object ID 202 identifying a data object 104 _(i); storage pool 204 in which the data object 202 is stored; a logical volume 206 in which the data object is stored, e.g., logical unit number (LUN), volume, logical drive, etc.; a timestamp 208 indicating a time the data object 202 was created and/or last modified; a file path 210, such as a directory name, including the data object 202; and a facet 400 _(i) for each data instance in the object 202 providing a description or classification of the data instance in the object 202 that is used to determine whether to redact the data instance from the object 202.

FIG. 3 illustrates an embodiment of a database record 300 _(i) in the database 300 and includes a record identifier (ID) 302 identifying the database record 300 _(i) in the database 300 and data object information 304, which may comprise all or some of the information in the event message 200 in fields of the database record 300 _(i). The database 300 may also include an index to allow fast searching of records 300 _(i) based on relevant backup key/value pairs, such as the time the database object was last updated, data type, source data set, etc.

FIG. 4 illustrates an embodiment of a data redaction facet 400 _(i) generated by a deep inspection module 109 _(i) for a data filed in an object including a data field or data instance in the object 402 and a redaction relevant facet 404 that may be used to determine whether to perform redaction of the data in the data instance.

FIG. 5 illustrates an embodiment of operations performed by an event manager 108 _(i) to generate an event message 200 for an update to a data object in a source data set 104 _(i) managed by the event manager 108 _(i). Upon receiving (at block 500) the update to a data object, the event manager 108 _(i) calls (at block 502) the deep inspection module 109 _(i) to perform deep inspection on the updated data object to determine facets for the updated data providing attributes and characterizations of instances of data in the updated object that can be used to determine whether the data instance should be redacted. The event manager 108 _(i) generates (at block 504) an event message 200 including information on the data object, such as the data object ID 202, storage 204 storing the data object 202, logical volume 206, timestamp 208, file path 210, and determined data redaction facets 400 _(i). The generated event message 200 is sent (at block 506) to the storage server 100 to dispatch to one of the message queues 124 ₁, 124 ₂ . . . 124 _(m).

With the embodiment of FIG. 5, the event manager 108 _(i) may generate the event message 200 immediately upon receiving the update to the data object before the update is applied to the storage 106 _(i). In this way, the event messages 200 provide real time information on updates to the data objects and updated facets for changes to data instances and fields in the data object to the storage server 100 so that the database 300 has current information on changed data objects and there facets.

FIG. 6 illustrates an embodiment of operations performed by the event message dispatcher 118 to process an event message 200 received from an event manager 108 _(i) having information on an update to a data object in a source data set 104 _(i). Upon receiving (at block 600) an event message 200, the event message dispatcher 118 adds (at block 602) the event message 200 to an event message queue 124 _(i). The event message queue 124 _(i) may be selected based on workload load balancing to evenly distribute messages 200 among the message queues or having storages assigned to message queues, so an event message is added to the message queue 124 _(i) associated with the storage 106 _(i) in which the data object 104 _(i) of the event message is stored.

FIG. 7 illustrates an embodiment of operations performed by a consumer 126 _(i) process to process one or more event messages 200 in a message queue 124 _(i). Upon a consumer 126 _(i) processing (at block 700) a message queue 124 _(i), the consumer 126 _(i) reads (at block 702) an event message 200 from the message queue 124 _(i). If (at block 704) the object indicated in the event message 200 is in the database 300, i.e., there is a record 300 _(i) for the object in the database 300, then the record 300 _(i) for the object is updated (at block 706) with new information in the event message 200, such as updated metadata (e.g., 204, 206, 208, 210) and updated facets 400 _(i) for data instances in the object. If (at block 704) there is no record 300 _(i) for the object indicated in the event message in the database 300, then the consumer 126 _(i) generates (at block 708) a database record 300 _(i) having a record ID 302 and database object information 304 comprising the information 202, 204, 206, 208, 210, 400 _(i) in the received event message 200. The generated database record 300 _(i) is stored (at block 710) in the database 300 and a database index according to an index key, such as a source data set, change timestamp, etc.

With the embodiments of FIGS. 5, 6, and 7, information on real-time updates to data objects are generated and provided to the storage server 100 to store in the database 300. In this way, the database 300 immediately reflects the current state of updates to data objects and facets to use to determine data to redact. Further, the event message dispatcher 118 receives event messages 200 from different storages 106 ₁, 10 ₂ . . . 106 _(n) to allow the database 300 to reflect updates to data objects in different storages 106 ₁, 106 ₂ . . . 106 _(n).

FIG. 8 illustrates an embodiment of operations performed by the data redaction module 128 to redact data from data objects indicated in received event messages 200 using the database 300. Upon initiating (at block 800) a data redaction operation, the data redaction module 128 queries (at block 802) the database 300 to determine updated objects, such as objects having a timestamp 208 greater than recent threshold time, that has at least one facet 400 _(i) for an instance of data matching a data type in the redaction rules 130. A match may comprise an exact or fuzzy (approximate) match of the facet 400 _(i) string and a string of a data type in the redaction rules 130 to redact. A match may also involve natural language processing and data mining to determine relatedness of terms within a degree of confidence. For each updated object 104 _(i) having a facet 400 _(i) matching a data type in redaction rules 130 indicating data to redact, a loop of operations is performed at block 804 through 810. At block 806, the data redaction module 128 determines all data instances in object 104 _(i) having facets 400 _(i) matching data types in the redaction rules 130 and then redacts (at block 808) the determined instances of data in the object 104 _(i). The redacted object 104 _(i) is then stored in the storage 106 _(i).

With the embodiment of FIG. 8, the database 300 is immediately updated with updated facets for updated objects by processing the event messages 200 in the message queues 124 ₁, 124 ₂ . . . 124 _(m), where the event messages 200 are immediately generated at the source servers 102 ₁, 102 ₂ . . . 102 _(n) upon modifications to the data objects. This allows for real-time immediate processing of updated data objects to determine if data needs to be redacted to provide for immediate compliance with data redaction rules 130. Further, because the database 300 provides real-time information on updated data objects, the data objects subject to data redaction indicated in the database 300 comprise the most recent modified data objects.

FIG. 9 illustrates an embodiment of operations to process new data types to redact from a redaction update service 132, which may provide alerts on new government or industry regulations and guidelines for data to redact. Upon receiving (at block 900) a new data type to redact from the redaction update service 132, the data redaction module 128 or other component adds (at block 902) the new data type as a redaction rule in the data redaction rules 130 to redact. The data redaction module 128 further queries (at block 904) the database 300 to determine any object information 300 _(i) having a facet 400 _(i) for an instance of data in the object matching the new data type. The operations at blocks 804-810 are then performed (at block 906) to redact any data instances having a facet matching that of the new data type to provide immediate redaction of the data and compliance with the new redaction rule.

With the embodiment of FIG. 9, updates of new data types to redact are immediately added to the data redaction rules 130 to immediately apply to objects 104 _(i) indicated in the database 300 to allow for immediate compliance to the new redaction data type, which may be required by a government or industry organization.

FIGS. 10, 11, and 12 illustrate an alternative embodiment where the changed data objects to subject to data redaction are determined directly from the event messages 200 in the message queues 124 ₁, 124 ₂ . . . 124 _(m) without having to query the database 300, which allows for a faster determination of the data objects to backup, such as in real time from when the data object was changed. In certain embodiments, the changed data object may be subject to redaction by processing from the message queue 124 _(i) even before the changed data object in a memory of the source servers 102 ₁, 102 ₂ . . . 102 _(n) has been written to the storages 106 ₁, 106 ₂ . . . 106 _(n).

FIG. 10 illustrates an embodiment of message queue subscriber information 1000 _(i) the event message dispatcher 118 maintains for each message queue 124 _(i) to determine consumers 126 ₁, 126 ₂ . . . 126 _(m) that subscribe to the message queues 124 _(i). The event message dispatcher 118 may maintain one instance of message queue subscriber information 1000 _(i) for each message queue 124 _(i). The message queue subscriber information 1000 _(i) includes a message queue 1002 and a list of zero or more subscribers 1004, i.e., consumers 126 ₁, 126 ₂ . . . 126 _(m), that are to be notified when an event message 200 is added to a message queue 124 _(i).

FIG. 11 illustrates an embodiment of operations performed by the event message dispatcher 118 after adding a received event message 200 to an event message queue 124 _(i), such as after performing the operations of FIG. 6. After adding (at block 1100) the event message 200 to the event message queue 124 _(i), the event message dispatcher 118 processes (at block 1102) the message queue subscriber information 1000 _(i) for the message queue 124 _(i) to which the event message 200 was added to determine a consumer 1004 subscribed to the message queue 1002. A notification is sent (at block 1104) to the determined subscribed consumers 1004 to process.

FIG. 12 illustrates an embodiment of operations performed by a consumer 126 _(i) or the data redaction module 128 to process the notification sent at block 1104 of an event message 200 _(i) added to the event message queue 124 _(i). Upon a subscribing consumer 126 _(i) receiving (at block 1200) the notification, the subscribed consumer 126 _(i) may perform itself or call the data redaction module 128 to read (at block 1202) the message 200 in the message queue 124 _(i) for which the notification was received. If (at block 1204) the event message 200 has a facet 400 _(i) for a data instance in the object 202 matching one of the data types in the redaction rules 130 _(i) then the redaction module 128 redacts (at block 1206) each instance of data in the object 202 having a facet 400 _(i) matching a data type in the redaction rules 130. If (at block 1204) there is no facet 400 _(i) in the event message 200 matching a data type in the data redaction rules 130, then control ends as there is nothing new to redact for the updated object 202 indicated in the processed event message 200.

In certain embodiments, multiple consumers may receive the notification of an event message 200 added to a message queue 120 _(i) to allow different consumers 126 _(i) and redaction module 128 to independently determine whether to redact data instances (fields) in an updated data object.

With the embodiment of FIGS. 10, 11, and 12, real-time reporting of changes to data objects in event message are processed by consumers 126 ₁, 126 ₂ . . . 126 _(m) subscribed to the message queue 124 _(i) to which the real-time event message 200 is added to allow for an immediate determination of whether the data object includes data instances to redact. In this way, there are no delays to determine whether to redact data fields in a data object after the object is updated because the object is considered for data redaction immediately upon the consumer being alerted of the change to the data object to process for redaction. Further, in certain implementations, because the event message 200 is provided immediately to the storage server 100 even before the changed data object is stored in the storage 106 _(i), the determination to redact data from the data object 104 _(i) may be performed before the changed data object at the source server 102 _(i) is written to the storage 106 _(i), such that the redacted data object may be provided to write to storage before the non-redacted version of the updated data object is written.

In the described embodiment, variables i, j, m, n, etc., when used with different elements may denote a same or different instance of that element.

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

The computational components of FIG. 1, including the storage server 100, hosts 110, source servers 102 ₁, 102 ₂ . . . 102 _(n), host 110, and redaction update service 132 may be implemented in one or more computer systems, such as the computer system 1302 shown in FIG. 13. Computer system/server 1302 may be described in the general context of computer system executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 1302 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.

As shown in FIG. 13, the computer system/server 1302 is shown in the form of a general-purpose computing device. The components of computer system/server 1302 may include, but are not limited to, one or more processors or processing units 1304, a system memory 1306, and a bus 1308 that couples various system components including system memory 1306 to processor 1304. Bus 1308 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 1302 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 1302, and it includes both volatile and non-volatile media, removable and non-removable media.

System memory 1306 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 1310 and/or cache memory 1312. Computer system/server 1302 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 1313 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 1308 by one or more data media interfaces. As will be further depicted and described below, memory 1306 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

Program/utility 1314, having a set (at least one) of program modules 1316, may be stored in memory 1306 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. The components of the computer 1302 may be implemented as program modules 1316 which generally carry out the functions and/or methodologies of embodiments of the invention as described herein. The systems of FIG. 1 may be implemented in one or more computer systems 1302, where if they are implemented in multiple computer systems 1302, then the computer systems may communicate over a network.

Computer system/server 1302 may also communicate with one or more external devices 1318 such as a keyboard, a pointing device, a display 1320, etc.; one or more devices that enable a user to interact with computer system/server 1302; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 1302 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 1322. Still yet, computer system/server 1302 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 1324. As depicted, network adapter 1324 communicates with the other components of computer system/server 1302 via bus 1308. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 1302. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the present invention(s)” unless expressly specified otherwise.

The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.

The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.

Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the present invention.

When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the present invention need not include the device itself.

The foregoing description of various embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims herein after appended. 

What is claimed is:
 1. A computer program product for determining data to redact in an object, wherein the computer program product comprises a computer readable storage medium having computer readable program code embodied therein that when executed performs operations, the operations comprising: receiving event messages for objects from a source server managing the objects in a storage, wherein the event messages include facets for data instances in the objects resulting from deep data inspection of the objects, wherein the facets associate data instances in the objects with redaction relevant attributes of the associated data instances that are used to determine whether the data instances for which the facets are provided should be redacted, wherein a facet indicates a redaction relevant attribute associated with a data instance in one of the objects; adding the event messages to a message queue; adding information to a database for the event messages in the message queue to include the facets for the objects in the event messages; maintaining redaction rules indicating data types to redact; querying the database to determine an object having a facet with a redaction relevant attribute matching one of the data types in the redaction rules; determining facets in the determined object having redaction relevant attributes that match the data types indicated in the redaction rules to redact; and redacting the data instances in the determined object indicated in the determined facets as associated with redaction relevant attributes that match the data types indicated in the redaction rules to redact.
 2. The computer program product of claim 1, wherein a facet that indicates data to redact comprises at least one of sensitive data, personally identifiable information, and financial information.
 3. The computer program product of claim 1, wherein an event message in a message queue includes metadata for an object indicating an object is an updated object, wherein the operations further comprise: adding the metadata from the event message for the object to the database, wherein the querying the database comprises querying the database for updated objects having facets with redaction relevant attributes matching the data types in the redaction rules.
 4. The computer program product of claim 1, wherein the object determined from querying the database comprises a first object, wherein the operations further comprise: receiving an update on a new data type to redact; querying the database to determine a second object having a facet having a redaction relevant attribute that matches the new data type; and redacting an instance of data from the determined second object the facet associates with the redaction relevant attribute matching the new data type.
 5. The computer program product of claim 4, wherein the operations further comprise: adding the new data type to the redaction rules.
 6. The computer program product of claim 1, wherein an event message includes metadata on an updated object, wherein the metadata on the updated object updates metadata for the object in the database, wherein deep data inspection is performed on the updated object to update facets for the updated object that is added to the database.
 7. The computer program product of claim 6, wherein event messages are generated immediately after a modification resulting in the updated object to provide information on real-time changes to updated objects to the message queue and the database.
 8. The computer program product of claim 1, wherein there are a plurality of message queues and consumer processes, wherein the consumer processes are assigned to process event messages from one of the message queues, wherein the message queues receive event messages for objects, wherein the operations further comprise: periodically invoking a consumer process to read the event messages in one of the message queues and add metadata and facets to the database for an object indicated in the read event messages.
 9. A system for determining data to redact in an object and in communication with a source server managing objects in a storage, comprising: a processor; and a computer readable storage medium having computer readable program code embodied therein that when executed by the processor performs operations, the operations comprising: receiving event messages for objects from the source server, wherein event messages include facets for data instances in the objects resulting from deep data inspection of the objects, wherein the facets associate data instances in the objects with redaction relevant attributes of data instances that are used to determine whether data instances for which the facets are provided should be redacted, wherein a facet indicates a redaction relevant attribute associated with a data instance in one of the objects; adding the event messages to a message queue; adding information to a database for the event messages in the message queue to include facets for the objects in the event message; maintaining redaction rules indicating data types to redact; querying the database to determine an object having a facet with a redaction relevant attribute matching one of the data types in the redaction rules; determining facets in the determined object having redaction relevant attributes that match the data types indicated in the redaction rules to redact; and redacting the data instances in the determined object indicated in the determined facets as associated with redaction relevant attributes that match the data types indicated in the redaction rules to redact.
 10. The system of claim 9, wherein a facet that indicates data to redact comprises at least one of sensitive data, personally identifiable information, and financial information.
 11. The system of claim 8, wherein the operations further comprise: receiving an update on a new data type to redact; querying the database to determine a second object having a facet having a redaction relevant attribute that matches the new data type; and redacting an instance of data from the determined second object the facet associates with the redaction relevant attribute matching the new data type.
 12. The system of claim 11, wherein the operations further comprise: adding the new data type to the redaction rules.
 13. The system of claim 9, wherein an event message includes metadata on an updated object, wherein the metadata on the updated object updates metadata for the object in the database, wherein deep data inspection is performed on the updated object to update facets for the updated object that is added to the database.
 14. The system of claim 13, wherein event messages are generated immediately after a modification resulting in the updated object to provide information on real-time changes to updated objects to the message queue and the database.
 15. The system of claim 9, wherein there are a plurality of message queues and consumer processes, wherein the consumer processes are assigned to process event messages from one of the message queues, wherein the message queues receive event messages for objects, wherein the operations further comprise: periodically invoking a consumer process to read the event messages in one of the message queues and add metadata and facets to the database for an object indicated in each of the read event messages.
 16. A method for determining data to redact in an object, comprising: receiving event messages for objects from a source server managing the objects in a storage, wherein the event messages include facets for data instances in the objects resulting from deep data inspection of the objects, wherein the facets associate data instances in the objects with redaction relevant attributes of the associated data instances that are used to determine whether the data instances for which the facets are provided should be redacted associate data instances in the objects with redaction relevant; adding the event messages to a message queue; adding information to a database for the event messages in the message queue to include the facets for the objects in the event messages; maintaining redaction rules indicating data types to redact; querying the database to determine an object having a facet with a redaction relevant attribute matching one of the data types in the redaction rules; determining facets in the determined object having redaction relevant attributes that match the data types indicated in the redaction rules to redact; and redacting the data instances in the determined object indicated in the determined facets as associated with redaction relevant attributes that match the data types indicated in the redaction rules to redact.
 17. The method of claim 16, wherein a facet that indicates data to redact comprises at least one of sensitive data, personally identifiable information, and financial information.
 18. The method of claim 16, wherein the object determined from querying the database comprises a first object, further comprising: receiving an update on a new data type to redact; querying the database to determine a second object having a facet having a redaction relevant attribute that matches the new data type; and redacting an instance of data from the determined second object the facet associates with the redaction relevant attribute matching the new data type.
 19. The method of claim 18, further comprising: adding the new data type to the redaction rules.
 20. The method of claim 16, wherein an event message includes metadata on an updated object, wherein the metadata on the updated object updates metadata for the object in the database, wherein deep data inspection is performed on the updated object to update facets for the updated object that is added to the database.
 21. The method of claim 20, wherein event messages are generated immediately after a modification resulting in the updated object to provide information on real-time changes to updated objects to the message queue and the database.
 22. The method of claim 16, wherein there are a plurality of message queues and consumer processes, wherein the consumer processes are assigned to process event messages from one of the message queues, wherein the message queues receive event messages for objects, further comprising : periodically invoking a consumer process to read the event messages in one of the message queues and add metadata and facets to the database for an object indicated in each of the read event messages. 